
Visual NodeFire
- There are two basic type of publishing... manual and auto. With a manual publish you will copy the menu code and paste it to your HTML source. The auto publish saves the code for you and automatically changes external file references accordingly.
- Each publish interface has a 'compress menu code' checkbox option. If you need your code to be manually editable and readable, make sure to un-check the feature before publishing.
- The varius publish interfaces refer to code that must be included directly in your HTML source as 'inline' or 'in page'.
- Menu code that is published to a seperate file is refered to as 'external' or 'seperate'
- Publishing the menus structure to an external file will not allow your links to be spidered by search engines. If you require SEO, choose the in-page or inline option for the structure. The inline structure may be added ta a server side include (ASP, PHP, etc...) for easy delivery to multiple documents.
- Any portion of the menu may be added to a server side include (ASP, PHP, etc...) for delivery to multiple documents.
- Positioning your menu within a constricted width will cause main horizontal items to wrap. The reason for this is that the scalability of the menu requires that there is enough container space to
accommodate the natural combined width of the menu items. If the width is not made available, horizontal main menu items will wrap to the next line. To overcome this, define a fixed width on the menus containing element, or re-work the HTML surrounding the menu so enough width is available to
accommodate the maximum space which may be occupied by the main items.
Copyright (c) 2012, OpenCube Inc., All Rights Reserved.